When you press the first button, Objects, Stack Tabulator collects all properties of a desired stack, its backgrounds, cards, fields, and buttons, and presents them in tabular form (hence the name, "Stack Tabulator"). (The gathering of this information can take quite some time, so be prepared to go do something else for a while.) The result might then start out looking like this:
 
At first this looks formidable, but it is really quite simple and handily presented.
We are told the stack name, and that the stack itself has a script; notice that this script is given a number, which will be coordinated with the numbers assigned to the scripts when we gather them later with the Scripts button. If the stack had had its CantModify property, or any of its other properties, set to True, we would also be told this now.
Next, we learn that there is only one background, that it has no title, and that it consists of cards 1, 2, and 3; this listing of the particular cards of a background is potentially important, because there is no rule that says that all the cards of a given background must come next to one another in a stack. This background has no script (if it had, we would be told now), and none of its properties is set to True (ditto).
There are no background fields or button (if there were, they would have been listed next, one background at a time, first fields then buttons), so now we start on each card, first its fields, then its buttons.
The first card, too, evidently has no script, and none of its properties is set to True.
The first field of that card (cd fld 1) has no title; its default font is Geneva 12, textHeight is 16, left-justified Alignment, and it is Visible; we are given its Rect, and told that it is a REctangular-type field. We also see that its LockText property is set to True. It also has some Text inside it; observe that this text is given a number, which will be coordinated with the numbers assigned to the field texts when we gather them later with the Field Texts button. It has no script (as we see from the last column). And so forth.
Before you start sweating over all the abbreviations at the top of each listing of fields and buttons, relax: the stack itself contains a reminder of what everything means, and you can toggle this information with the tabular listing itself, by using the Display File button, whose name will appear as Help when a file listing is showing.
The Field Texts button gathers the texts of the fields; unfortunately, any text-formatting applied to individual letters is lost (I can see a way to prevent this, but the program would become insanely slow, so I havenΓÇÖt bothered). The Scripts button gathers the scripts. In both cases, the texts or scripts are gathered in an order, and assigned numbers, corresponding to that of the listing from the Objects button.
After pressing each button, you can look over the results in the scrolling field on the card. Observe that you lose immediate access to the earlier information when you press a new button. However, you do not lose the information itself; it resides in a textfile (three textfiles after you have pressed all three buttons), where you can consult or print it later from a word processor.
